Remove polyfills#12161
Conversation
…ning files The .devcontainer/ files were a Codespaces-specific overlay; the modernization plan now relies on the repo's docker-compose.yml + local .env instead. The .gitignore additions cover AGENTS.md, MODERNIZATION-PLAN-v2.md, and PROJECT-SUMMARY.md, which are explicitly local-only and must never be tracked.
…ad, PHPMailer/POP3) The PHP 8.5 floor makes every polyfill in this commit dead code: - sodium_compat: sodium is now a required extension (ext-sodium in composer.json), so the bundled polyfill tree and its compat.php / update-core.php / file.php hooks are no longer reachable. The verify_file_signature() sodium-compat speed-test block in wp-admin/includes/file.php is also removed — the sodium extension is always loaded on 8.5+. - class-json.php: Services_JSON is a PHP 5-era JSON polyfill. PHP 8.5 has json_encode/json_decode natively. No core callers. - class-snoopy.php: Snoopy is a 2000s-era HTTP client. WP_Http in class-wp-http.php is the modern replacement and is what core uses. - spl-autoload-compat.php: deprecated since 5.3, only contained a deprecation notice. No callers. - PHPMailer/POP3.php: bundled but unused by PHPMailer core (the active classes are class.phpmailer.php, class.smtp.php, etc.). - random_compat: not present in this checkout, but its entry in update-core.php's file inventory is removed for consistency, and a stale @SInCE comment in pluggable.php is updated. composer.json is lifted to PHP 8.5 with ext-sodium, ext-mbstring, and ext-mysqli declared as required. phpunit.xml.dist's coverage-exclude list is updated to drop the deleted files.
|
Hi there! 👋 Thank you for your contribution to WordPress! 💖 It looks like this is your first pull request to No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making. More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook. Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook. If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook. The Developer Hub also documents the various coding standards that are followed:
Thank you, |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @cbuntingde. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Trac Ticket MissingThis pull request is missing a link to a Trac ticket. For a contribution to be considered, there must be a corresponding ticket in Trac. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. More information about contributing to WordPress on GitHub can be found in the Core Handbook. |
1 participant
No description provided.